Part Number Hot Search : 
MPC560XB CBB65 30402 MMSZ5242 N82S126A 11N60 A2630 74AUP2G
Product Description
Full Text Search
 

To Download MAS3690CS Datasheet File

  If you can't view the Datasheet, Please click here to try to view without PDF Reader .  
 
 


  Datasheet File OCR Text:
  ma3690/1/3 1/41 the ma3690/1 chip set has three modes of operation: remote terminal, bus controller, and passive monitor it has a dual bus capability, requires minimum support hardware / software and is implemented on a radiation hard, cmos/sos process. for applications requiring access to terminal flag, a 48-pin dil ma3693 is available as an alternative to the ma3690. as a remote terminal, the ma3690/1 is fully compatible with mil-std-1553b. the chip set obtained seafac approval in december 1987. all options and mode commands specified by the mil std are implemented full and meaningful use is made of status word bits and a comprehensive bit word is provided. a unique mechanism has been incorporated that allows the subsystem to declare illegal commands legal, and vice versa, before the chip set services the command. it should be noted that use of this mechanism is optional and that the system defaults to normal operation if the option is not required. the chip set is easily interfaced to subsystem memory and is sufficiently flexible to ensure compatibility with a wide range of microprocessors. as a bus controller the ma3690/1 has the ability to initiate all types of 1553b transfer on either of the two buses an instruction word is set up by the subsystem, prior to transmission, which contains details of transfer type and bus selection. four bits of the instruction word have been used to specify the conditions under which the chip set will generate a subsystem interrupt. the most significant bits of the instruction word have been used to specify the conditions under which the chip set will perform an automatic retry and the number of retries to be carried out (max. 3). at the end of each instruction execution cycle, the chip set writes a report word into the subsystem memory; the contents of which give the subsystem an indication of the degree of success of the transfer. the bus controller may be used in either of two configurations, i.e. single shot or table driven. in the single shot configuration, the controller is under direct control from the subsystem (processor). in table driven configuration, the controller is given greater autonomy to execute a table of instructions held in either rom or ram. as a passive monitor, the chip set will monitor all bus activity and pass any associated information to the subsystem. as the name implies, in this mode of operation, the chip set is truly passive and will not reply to command instructions. features n radiation hard to 1mrads (si) n high seu immunity, latch-up free n cmos-sos technology n all inputs and outputs fully ttl or cmos compatible n military temperature range -55 to +125 c n dual bus capability n minimal subsystem interface n powerful bus control facility n complete remote terminal protocol n seafac approved signal descriptions all signals are ttl compatible unless stated otherwise. an n at the end of the signal name denotes an active low signal. supplies vdd 5 volts positive supply vss ground clock inputs ck12 12mhz clock bus interface lines pdin0 input positive threshold exceeded on bus 0. ndin0 input negative threshold exceeded on bus 0. txen0n output transmit enable for driver on bus 0. pdout0n output positive manchester data for driver on bus 0. ma3690/1/3 1553b bus controller/remote terminal replaces june 1999 version, ds3587-4.0 ds3587-5.0 january 2000
ma3690/1/3 2/41 ndout0n output negative manchester data for driver on bus 0. pdin1 input positive threshold exceeded on bus 1. ndin1 input negative threshold exceeded on bus 1. txen1n output transmit enable for driver on bus 1. pdout1n output positive manchester data for driver on bus 1. ndout1n output negative manchester data for driver on bus 1. subsystem interface lines stroben output strobe - information transfer strobe pulse for words being transferred on the data highway. bufenn output buffer enable - this line goes low to enable the data highway buffer between the terminal and the subsystem. r/wn output read/write - this line indicates the direction of information transfer between the terminal and the subsystem. when low, information is being written from the terminal to the subsystem. dtrqn output data transfer request - this line goes low to request permission to transfer a non mode data word to or from the subsystem. dtakn input data transfer acknowledge - this line should be driven low to grant permission to perform the requested data word transfer. mdtn output mode data transfer - rt: this line goes low to indicate that the data word being transferred is assosiated with a mode command. bc: when operating as a passive monitor this line goes low to indicate that a valid data word is on the data highway and should be written into the received data latch. gbrn output good block received - when in rt mode this line will pulse low to inform the subsystem that the received non mode data words are valid and may be used. adenn output address enable - when in rt mode this line will go low as part of the reset routine to enable the terminal address on to the data highway. syncn output synchronise - this line will pulse low if a valid synchronise mode command without data is received and passes all validity checks. statenn output status enable - rt: when low this line enables the contents of the subsystem status latch on to the data highway. bc: when low this line enables the bc report word on to the data highway. mdrn output mode data received - this line will pulse low to inform the subsystem that the received mode data is valid and may be used. rxcmdn output received command - rt: this line goes low to indicate that a valid command word for this rt is on the highway and should be written into the command word latch. bc: when operating as a passive monitor this line goes low to indicate that a valid command / status word is on the data highway and should be written into the received status latch. busyreqn / haltreqn input busy request / halt request - rt: this line should be driven low as a request for the terminal to set the busy bit and inhibit non mode data transfers to or from the subsystem. bc: this line should be driven low as a request for the terminal to halt table execution and all subsystem access. busyackn / haltedn output busy acknowledge / halted - rt: this line will go low to indicate that the subsystem has free access to the shared store. bc: this line will go low to indicate that all terminal operation has been halted and hence the subsystem has free access to the shared store. codenn output code enable - this line when low indicates that a word transfer between the terminal and either the instruction store or the report store is taking place. c0 output code 0 - this line is the least significant address line from the terminal to the instruction and report stores. c1 output code 1 - this line is the least significant but one address line from the terminal to the instruction and report stores.
ma3690/1/3 3/41 incadrn output increment address - this line pulses low to increment the external instruction addressing counter. hsfn/irqn output handshake fail / interrupt request rt: this line pulses low to inform the subsystem that it has not responded to a data transfer request to take place. bc: this line pulses low to generate an interrupt to the bc subsystem processor. incmdn output in command - when low this line indicates that the terminal is currently servicing a command word. eotn output end of transmission - when low this line indicates that the selected bus is quiet and hence available for use. abortn output this line will pulse low to abort execution of the current command if an error is detected. b0-b15 input/output highway lines - 16 line bidirectional output data highway. (b0 = lsb). cldn inter-chip (cmos) command load - when low this line indicates that the word on the data highway should be loaded into the transmitter for transmission with a command sync. dldn inter-chip (cmos) data load - when low this line indicates that the word on the data highway should be loaded into the transmitter for transmission with a data sync. obfn inter-chip (cmos) output buffer full - when low this line indicates that the transmitter output buffer is full and cannot be overwritten. valdrn inter-chip (cmos) valid data received - when low this line indicates that a valid data word has been received and is on the data highway. valcrn inter-chip (cmos) valid command received - rt: when low this line indicates that a valid command word for this rt has been received. bc: when low this line indicates that a valid word with a command sync has been received. rt/bcn input remote terminal/bus controller - when high the terminal will function as an rt.when low the terminal will function as a bus controller. ck4 output 4mhz system clock. pucn input power up clear - this line should be pulsed low following power-up. resetn input/output reset - this line when low, forces the internal circuitry to reset to the quiescent initialised state. this is a ttl level input on both devices and an open-drain output on the ma3690. the subsystem should drive this line via an open drain/collector device with external pull up fitted. rt0 / rt1 inputs reply timeout decode - these lines on the ma3690 allow four different timeout values to be used. on the ma3693, the rt1 signal is not available and is pulled down internally. rt1 rt0 timeout (us) 00 16 01 22 10 44 1 1 108 note: under normal operation, option 00 should be used. (i.e. 16us) the measurement is taken between mid parity and mid sync - measured at pdin/ndin terminals. tf output terminal flag - this line is available only on the 64-pin ma3690 and on the ma3693 (where it replaces rt1). the line indicates the state of the terminal flag bit in the status word, and can be inhibited by the mode code inhibit terminal flag. this is an active low signal. test/sot inputs these lines are for test purposes only and for normal chip set operation must both be tied low.
ma3690/1/3 4/41 operation in bus control mode for this mode of operation the rt/bc pin must be held in the logic zero state. on power up the puc or reset line must be pulsed low for a minimum of 500ns causing the chip set to initialise and assume the halted state with the halted output low. to release the terminal from the halted state, the subsystem must drive the haltreq line through a low to high transition, at which time the halted line will go inactive. when the halted line goes inactive,the terminal will address a four word deep instruction store as shown below, using the c0 and cl outputs. this first instruction after a reset is a noop. instruction store c1 c0 word 0 0 instruction 0 1 receive command 1 0 transmit command 1 1 data pointer the instruction word specifies the operation which the terminal is to carry out, and is formatted in the following way: instruction word bit 15.14. 13.12.11. 10.9.8.7. 6.5. 4.3. 2.1.0. retry retry interrupt bus functlon message count condition conditlon select code code the significance of the instruction word bits are as follows: message code code transfer type 000 rt to bc 001 bc to rt 010 rt to rt, data to bc subsystem 011 rt to rt, no data to bc subsystem 100 broadcast rt to bc, non data mode commands only 101 broadcast bc to rt 110 broadcast rt to rt, data to bc subsystem 111 broadcast rt to rt, no data to bc subsystem mode codes without data are followed by a noop. function code code terminal function 00 execute message code 01 perform self test 10 monitor bus 11 no operation (noop) the function code (bits 4 and 3 of the instruction word) specifies the required terminal mode of operation. execute - code 00 with the function code bits set to 00, the terminal will execute the message as defined in the message code bits self test - code 01 if the terminal has been selected to perform a self test then the terminal transmitter output stages will be disabled and the self test sequence entered. at the end of the self test the transmitter stages will be re-enabled and a report sequence will be activated, in order to report on the success, or failure, of the self test. passive monitor - code 10 if the function code of the instruction word is 10 the terminal will disable the transmitter output stages, suspend table execution and merely monitor the specified bus for valid words. no operation - code 11 the no operation code provides a means of introducing delay or a wait sequence into the table operation. in selecting this code the terminal will be forced into the report sequence and provide either an increment signal (incadrn) or an interrupt (irqn) if the interrupt always flag in the instruction word has been selected. bus select code definition 00 transmit on bus 0 01 transmit on bus 1 note: bit 6 of the instruction word is tied low internally. the required data bus on which transactions take place is defined by bit 5. in addition to this, this bit defines the bus on which the transmitter self test operation will be conducted and the choice of the bus for monitor purposes in passive monitor mode. interrupt condition code definition 0001 interrupt if no response 0010 interrupt if status bit set 0100 interrupt always 1000 interrupt if word error if the terminal detects one of the above conditions and the appropriate flag is set, the the irq line will pulse low for 250ns.
ma3690/1/3 5/41 four bits of the instruction word (bits 10-7) define conditions under which the terminal will generate an interrupt to the subsystem (irqn). note that the generation of irqn will only take place after any selected retry conditions have been exhausted. the interrupt conditions which may be selected can be categorised as follows: 1. interrupt if no response - the terminal will generate an interrupt if the rt does not respond. 2. interrupt if status bit set - the terminal will generate an interrupt if a received status word has a bit set other than in the rt address field or if the wrong rt responds. 3. interrupt always - the terminal will generate an interrupt regardless of whether the message was successful or not. 4. interrupt if word error - the terminal will generate an interrupt if a word encoding or word count error occurs. in all of the above cases, the terminal will generate a 250ns pulse on irqn and enter the halted state. this will occur after the report sequence has been executed. note the incadrn will not be produced. retry condition code definition 001 retry if error 010 retry if status bit set 100 retry if busy set three bits of the instruction word (bits 13-11) are used as flags to specify conditions under which the terminal will execute automatic message retries until the retry number count is zero. the retry flags are involved with the following conditions: 1. retry if error - this includes a no-status response, a word encoding error, or a wrong word count from a responding rt. 2. retry if status bit set - an automatic retry will take place if a received status word has a bit set, other than in the rt address field, or if the wrong rt responds. 3. retry if busy - this is a specific check for the setting of the busy bit in a responding rts status word. the remaining two bits of the instruction word specify the number of message retries which the bus controller will attempt automatically. a code of 00 specifies no retries, a code of 11 specifies the maximum of three retries. the retries are in addition to the initial message transmitted, hence a message may be transmitted four times in total, if not successful. note that if the condition which is being tested becomes invalid, the retry sequence will discontinue on the next message with the bus controller completing execution of the message in the relevant manner. retry count the two most significant bits of the instruction word specify the number of retries to be carried out when a retry condition has been detected. (maximun 3 given by code 11) receive command word the receive command word is addressed when codenn and c1 are both low and r/wn and c0 are both high. this word is the command word which will be transmitted for a bc to rt transfer or as the first command word of an rt to rt transfer. note: this word should be set to 1111 hex if the message code is 000 or 100, or if the function code is not 00. transmit command word the transmit command word is addressed when codenn and c0 are both low and r/wn and c1 are both high. this word is the command word which will be transmitted for an rt to bc transfer or as the second command word of an rt to rt transfer. note: this word should be set to 1111 hex if the message code is 001 or 101, or if the function code is not 00. data pointer word the data pointer word is addressed when codenn is low and c0, c1 and r/wn are all high. this word is intended as a base address pointer to the subsystem data store thus specifying where any data words associated with the current instruction should be stored or retrieved from. as such, this word is not read into the terminal itself but is merely transferred from the instruction store to a suitable external address latch. (the bufenn signal is therefore inactive during this transfer).
ma3690/1/3 6/41 report store the report store holds information concerning the success or failure of the execution of the last instruction, and is addressed by means of the codenn, c0 and c1 lines as for the instruction store the report store is addressed when the r/ wn line is low, the instruction store when the r/wn line is high. the report store comprises a report word, a receive status word (if applicable) and a transmit status word (if applicable). the fourth location has no meaning and is not at anytime addressed. c1 c0 word 0 0 report word 0 1 rx status word 1 0 tx status word 1 1 not used report word the report word gives the subsystem information as to the type of error associated with the last transfer (the word will be clear if no error occurred). the report word is formatted as follows: the report word is written at the end of message execution, after all retries have been exhausted and prior to the irqn line being set active this word indicates the health of the terminal as well as information relating to the message execution. transmitter timeout error this bit will be set if a transmitter timeout error occurs while the terminal is transmittting or if a self test on the transmitter timeout mechanism fails. this will come into effect 800us after the commencement of the self test. the setting of this bit will also cause a subsystem interrupt to be generated. this bit will be reset to logic zero if the terminal is reset. subsystem handshake failure this bit will be set if the subsystem fails to acknowledge a terminal request to transfer a data word in 0.75us for a received data word or 13.5us for a transmit data word. if this condition takes place while the terminal is transmitting the transmission will be aborted. the setting of this bit will also cause a subsystem interrupt to be generated.. this bit will be reset to logic zero if the terminal is reset. loop test failure this bit will be set if the receiver circuitry detects an absence of terminal transmission or a waveform encoding error occurs while the terminal is transmitting. the seting of this bit while the terminal is transmitting will cause the transmission to be aborted and a subsystem interrupt to be generated. this bit will be reset to logic zero if the terminal is reset. programmed halt this bit will be set if the interrupt always flag of the instruction word has been selected. this bit will be reset at the start of each new instruction execution cycle. retry used this bit will be set if one or more message retries has been attempted. this bit will be reset at the start of each new instruction execution cycle. word count low this bit will be set if the terminal detects fewer valid data words than specified by the transmit command word of the instruction set. this bit will be set low at the start of each instruction execution cycle or message retry. word county high this bit will be set if the terminal detects more valid data words than specified by the transmit command word of the instruction set. this bit will be set low at the start of each instruction execution cycle or message retry. command error this bit will be set if an error occurs in the instruction set. the setting of this bit will cause instruction execution to be aborted and a subsystem interrupt to be generated. this bit will be reset at the start of each new instruction execution cycle. 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 continuous bus traffic 0 tx timeout bus 1 tx timeout bus 0 rx status flag rx status missing tx status flag tx status missing command error word count high word count low retry used programmed halt loop test fail ss handshake fail tx timeout error
ma3690/1/3 7/41 tx status missing this bit will be set if a no-response is detected from an rt which has been commanded to transmit and the relevant rt address was not the broadcast address. this bit will be reset at the start of each new instruction cycle or message retry. tx status flag this bit will be set if the status word received from a transmitting rt has a bit set or has the wrong terminal address. this bit will be reset at the start of each new instruction execution cycle or message retry. rx status missing this bit will be set if a no-response is detected from an rt which has been commanded to receive and the relevant rt address was not the broadcast address. this bit will be reset at the start of each new instruction cycle or message retry. rx status flag this bit will be set if the status word received from a receiving rt has a bit set or has the wrong terminal address. this bit will be reset at the start of each new instruction execution cycle or message retry. transmitter timeout on bus 0 this bit will be set if the transmitter timeout mechanism operates on bus 0. this will be set under self test execution with bus 0 selected in the instruction word. this bit will be reset to logic zero if the terminal is reset. transmitter timeout on bus 1 this bit will be set if the transmitter timeout mechanism operates on bus 1. this will be set under self test execution with bus 1 selected in the instruction word. this bit will be reset to logic zero if the terminal is reset. continuous bus traffic this bit will be set if the terminal detected that the data bus is already active when the bc is instructed to execute a message on that data bus. an active data bus is defined as a data stream of one command word or status word and greater than 32 continguous data words being received by the terminal. the setting of this bit will cause transmission to be suppressed and a subsystem interrupt to be generated. it should be noted that: 1. this condition is only likely to be caused by a runaway rt which transmits continuously. 2. if this condition is present the subsystem is able to specify the use of the alternative bus for its transmissions. this bit will be reset to logic zero when the terminal is reset or when the terminal detected a quiet bus. receive status word the receive status word location is addressed when codenn, c1 and r/wn are low and c0 is high. this location is used by the terminal to store the status word, if any, received from a receiving rt. in self test mode this location is updated with the contents of the receive command word during the instruction fetch cycle. transmit status word the transmit status word location is addressed when codenn, c0 and r/wn are low and c1 is high. this location is used by the terminal to store the status word, if any, received from a transmitting rt. in self test mode this location is updated with the contents of the transmit command word during the instruction fetch cycle. modes of operation the bus controller may be controlled in either a single shot mode or in a table driven mode. in the former, the execution of the message table would be under direct control of the subsystem, on a message by message basis. the table driven mode would provide a subsystem capable of more autonomous operation, leading to a greatly reduced level of processor intervention in the message execution level, at least. in either case the procedure of instruction fetch, message execute and reporting would be the same. the difference arises from the value of the haltreqn line when it is resampled at the end of message execution. this is further described below. single shot operation to commence a message execution the subsystem must take the haltreqn line low to high for a minimum of 1us. this will be followed by the terminal acknowledging this action by the haltedn line being set inactive (high). the haltedn line will remain high until the message has been completed, at which time the haltreqn line is further sampled. if it is low then the terminal will halt and wait until the request line is taken high again, in effect a single instruction execution. it is important to the integrity of the system that the haltreqn line is strictly glitch free, otherwise problems will arise with the terminal attempting to execute commands at a time when no terminal access to the various stores can be guaranteed.
ma3690/1/3 8/41 continuous operation the continuous message table operation mode can be achieved by ensuring that at the end of a message the haltreqn line is high. thus, assuming that the message has executed correctly, the terminal will generate a signal to increment the external address counter (incadrn) and continue to the next instruction. if, however there has been an interrupt generated (irqn active) the terminal will halt in the haltedn state until specifically requested to continue. note that no address increment will take place. to continue execution the haltreqn line should be taken low to high for the appropriate time. continuous table driven operation results in an intermessage gap of 20us. figure 1 shows the instruction fetch and execute cycle. figure 1: bc instruction fetch and execute cycle has haltreq gone low to high ? no yes set halted high fetch instruction message command error ? yes no execute instruction retry required ? retry count = 0 ? yes no yes no decrement retry count output report word int. required ? yes no pulse irq increment instruction address haltreq = 0 ? yes no set halted low
ma3690/1/3 9/41 passive monitor the terminal may be configured into a passive monitor (or bus monitor) merely by selecting the appropriate function code of the instruction word. by doing this the terminal will not take part in any further instruction execution but instead will monitor the selected bus for data transmissions. interrupt / retry capability the terminal has certain in-built functions which permit the terminal to retrieve situations which would normally cause a greater degree of subsystem intervention. this is achieved by having an automatic retry facility in-built to the terminal which is selectable from the instruction word. in this case both the condition and number of attempts for which the terminal must try may be specified. after completion of the required number of attempts, terminal operation may be halted with the possibility of an interrupt generated also. the interrupt facility provides a means of more direct subsystem interaction in the event of a failure. similar flags are required to be set in the instruction word before a selectable interrupt may be generated. this form of interrupt also includes an interrupt always flag whose application may be used to determine subsystem/system timing requirements. it should be noted that an interrupt may also be generated by the error checking procedures of the terminal which verify aspects of the instruction word and associated receive/ transmit command words. standby bus controller the terminal provides a number of signals to the subsystem for message addressing and execution. two address lines are provided (co, cl) plus a signal to increment an external counter (incadrn). this, together with the on- chip sequencing, error checking, etc., enables a standby bus controller, using a fixed table of messages, to be realised in few devices as shown in figure 2. it is therefore possible to attain a standby bc on a single 6 x 4 pcb card. figure 2: standby bus controller
ma3690/1/3 10/41 full bus controller to make use of the sos chipsets capabilities a processor- based system would be more applicable. a block diagram of such a system, using shared store technique is shown in figure 3. in this, the instruction word store would be alterable by the processor for use in various system conditions, i.e. a basic message table would initialy be set up with the processor monitoring the results of execution from the report word store and / or the interrupt request (irqn) line. on detection of an erroneous condition, the processor could write a new message table to test the rt in error by, for example, a self test mode command. the inclusion of automatic retry, with a maximum of 3 retries, in the instruction word, removes the requirement from the processor to retry under simple rt faults, e.g., status bit set. figure 3: full bus controller
ma3690/1/3 11/41 subsystem interface the terminal / subsystem interface consists of a 16 bit bidirectional data highway and a number of control lines, many of which are of optional use. the subsystem lines have been arranged such as to allow a simple shared store technique to be readily implemented but sufficient flexibility has been designed to allow optimisation of the interface for a particular subsystem design. remote terminal mode on initialisation, the rt address, address parity and broadcast enables are loaded from the subsystem via the data highway, figure 4. the subsystem status bits are also loaded in a similar manner when required, figure 5. this terminal uses two distinct methods for dealing with non mode data and mode data. in the first, a busy request / acknowledge handshake is used to ensure no data transfer takes place when the subsystem is busy thus ensuring no addressing / data conflict of the main data store. mode data, however, may be transferred even if the subsystem has declared itself busy. this represents a departure from previous chipset philosophy. the validation of a data transfer also depends on data type. for non mode data, a data transfer request / acknowledge handshake is used to transfer each data word to or from the subsystem (both rt and bc) with a good block received (gbrn) denoting a correct transfer. for mode data, a mode data transfer (mdtn) is used to signal a mode data word with correct transfer being denoted by mode data received (mdrn). thus, dependant on application, the l/o signals may be significantly reduced. an rt subsystem interface signal transfer is shown in figure 6. bit word the terminal contains a 16 regisiter, called bit word, which records message errors and terminal status information. the entire bit word contents are reset by power up initialisation or a legal mode command to reset remote terminal. the conditions for the setting of the bit, and any additional reset conditions are given for each signal. the contents of the bit word register shall not be altered by any of the following legal mode commands. transmit status word (tsw), transmit last command (tlc) and transmit bit word (tbw). transmitter timeout error this bit shall be set to logic one if transmitter timeout occurs while the terminal is tranmitting. in addition, if the terminal is issued with a legal mode command to initiate self test (code 00011) this bit shall be set if the range transmitter timeout mechanism does not operate within the of 660 m s to 800 m s. subsystem handshake failure this bit shall be set to logic one if the subsystem does not acknowledge a terminal request to transfer a data word in time for the transfer to take place correctly. loop test failure at all times while the terminal is transmitting the relevant receiver circuitry checks for an absence of transmission or any sync, manchester, parity or contiguity error in the terminals transmission. this bit shall be set to logic one if any of these error conditions are detected. illegal t/r bit this bit shall be reset to logic zero by the reception of any valid command word with the exception tsw,tlc and tbw. this bit shall be set to logic one if a valid mode command is received with a transmit/receive (t/r) bit opposite to that specified by mil-std-1553b. illegal command this bit shall be reset to logic zero by the reception of any valid command word with exceptions tsw, tlc and tbw. this bit shall be set to logic one if any of the following conditions arise: (a) the illegal command line to the subsystem status latch is low at the time when incmd goes active low. (b) a valid mode command is received with a reserved mode code and the allow code line to the subsystem staus latch is high at the time when incmd goes low. (c) an illegal transitter shutdown mode command is received. 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 0 0 tx timeout bus 1 tx timeout bus 0 terminal flag inhibited 0 bus 1 shutdown bus 0 shutdown illegal broadcast word count high word count low illegal command illegal t/r bit loop test failure ss handshake failure tx timeout error
ma3690/1/3 12/41 word count low this bit shall be reset to logic zero by the reception of any valid command word with the exception of tsw, tlc and tbw. this bit shall be set to logic one if fewer valid data words are received than specified by the preceding command word. word count high this bit shall be rest to logic zero by the reception of any valid command word with the exception of tsw, tlc and tbw. this bit shall be set to logic one if the received message is longer than stipulated by the preceeding command word. illegal broadcast this bit shall be reset to logic zero by the reception of any valid command word with the exception of tsw, tlc and tbw. this bit shall be set to logic one if a valid command word which by definition requires terminal transmission is received with the broadcast address. bus 0 shutdown this bit shall be set to logic one if bus 0 is shutdown. bus 1 shutdown this bit shall be set to logic one if bus 1 is shutdown. terminal flag inhibited this bit shall be set to logic one if the internal terminal flag inhibit is set. transmitter timeout on bus 0 this bit shall be set to logic one if a transmitter timeout has occured on bus 0. transmitter timeout on bus 1 this bit shall be set to logic one if a transmitter timeout has occured on bus 1. note: rtad0, rtad1, rtad2, rtad3, rtad4 define the rt address rtadpar odd parity with the address bits bcsten0 - broadcast enable for bus0 bcsten1 - broadcast enable for bus1 figure 4: subsystem rt address buffer rtad0 rtad1 rtad2 rtad3 rtad4 rtadpar buffer b0 b1 b2 b3 b4 b5 bcsten0 bcsten1 b6 b7 aden en
ma3690/1/3 13/41 figure 5: subsystem status latch figure 6: remote terminal subsystem interface signal transfer sserr - a low will cause the subsystem flag to be set in the terminal status word. servreq - a low will set the service request bit of the terminal status word. illegal command - allows the subsystem to declare any command word illegal. when low the terminal will inhibit data transfers to or from the subsystem, and after message validation will respond with the message error bit set in the terminal status word. allow code - provides the subsystem with the capability to declare any of the reserved mode codes as being meaningful. if a reserved mode code is received when high the command is treated as illegal and after message validation responds with me bit set in the terminal status word. if low the most significant bit of the mode code and the t/r bit determine whether any data words are involved and their direction. res0 , res1 , res2 - provides the subsystem the capability of setting any of the currently reserved bits of the terminal status word. dbacc - dynamic bus acceptance. if low then the dynamic acceptance bit of the terminal status word will be set in response to a legal mode command for dynamic bus control allocation. after switching to the bc mode of operation the first instruction must be a noop. dbcacc sserr servreq illegal commands allow code res0 res1 res2 b0 b1 b2 b3 b4 b5 b6 b7 g oe transparent latch statenn incmdn
ma3690/1/3 14/41 bus controller mode for data transfers generally, 750ns enable signals (bufenn,r/wn etc.) are produced by the terminal with a 250ns strobe signal upon which the data will be valid. the bus controller terminal provides signals to fetch the message and write out a report and any associated data. the haltreqn and haltedn handshake lines operate in a similar fasion to the busyreqn / busyackn rt lines in that if haltreqn is taken low the terminal will complete the current instruction and then halt, taking haltedn low to indicate that it has done so a bc subsystem may be operated in either a single shot or table driven mode. in either case, the two least significant address lines (c0,c1) to the instruction and report word stores are provided by the terminal. on taking haltreqn high (for a minimum of 1us) the subsystem initiates an instruction fetch cycle which consists of the terminal reading the instruction word, receive command word and transmit command word from the instruction store and transferring the data pointer word from the instruction store to an external data address latch. further operation is dependent on the instruction word. on executing a message sequence the terminal will write out the report word and either: 1. increment the instruction address and proceed to the next instruction, 2. increment the instruction address and halt, 3. do not increment the instruction address, interrupt subsystem and halt. any data associated with the command will be transferred to or from the data store in a similar manner as used by the rt. figure 7: bus controller subsystem interface signal transfer
ma3690/1/3 15/41 figure 8: chip set interconnection diagram
ma3690/1/3 16/41 subgroup definition 1 static characteristics specified in figure 11 at +25 c 2 static characteristics specified in figure 11 at +125 c 3 static characteristics specified in figure 11 at -55 c 7 functional characteristics specified at +25 c 8a functional characteristics specified at +125 c 8b functional characteristics specified at -55 c 9 switching characteristics specified in figure 12 at +25 c 10 switching characteristics specified in figure 12 at +125 c 11 switching characteristics specified in figure 12 at -55 c dc characteristics and ratings parameter min max units supply voltage -0.5 7 v input voltage -0.3 v dd +0.3 v operating temperature -55 125 c storage temperature -65 150 c note: stresses above those listed may cause permanent damage to the device. this is a stress rating only and functional operation of the device at these conditions, or at any other condition above those indicated in the operations section of this specification, is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. figure 10: absolute maximum ratings total dose radiation not exceeding 3x10 5 rad(si) symbol parameter conditions min typ max units v dd supply voltage - 4.5 5.0 5.5 v v ih1 ttl input high voltage - 2.0 - - v v il1 ttl input low voltage - - - 0.8 v v ih2 cmos input high voltage - 3.5 - - v v il2 cmos input low voltage - - - 1.5 v v oh1 ttl output high voltage i oh = -1ma v dd -0.4 - - v v ol1 ttl output low voltage i ol = 2ma - - 0.4 v v oh2 cmos output high voltage i oh = -1ma v dd -0.4 - - v v ol2 cmos output low voltage i ol = 2ma - - 0.4 v i il1 input low current v in = v ss (note 1) - - -10 m a i ih1 input high current v in = v dd (note 1) - - 10 m a i il2 input low current (rt1) v in = v ss (note 1) - - -50 m a i ih2 input high current (rt2) v in = v dd (note 1) 50 - 150 m a i ozl io low current v in = v ss (note 1) - - -50 m a i ozh io high current v in = v dd (note 1) - - 50 m a i dd power supply current - - - 25 ma v dd = 5v 10%, over full operating temperature range. note 1: guaranteed but not tested at -55 c mil-std-883, method 5005, subgroups 1, 2, 3 figure 11: electrical characteristics figure 9: definition of subgroups
ma3690/1/3 17/41 symbol description min. typ. max. units t1 ck4 to bus [b0:b15] valid 235 ns t2 ck4 to bus [b0:b15] high impedance 220 ns t3 b0: b15 set up wrt stroben - 15 ns t4 b0: b15 hold wrt stroben - 25 t5 valcrn to rxcmdn 3t t6 pulse width rxcmdn, r/wn, statenn, 3t bufenn, cldn, dldn, mdtn, codenn t7 pulse width stroben, gbrn, mdrn, syncn, irqn 1t t7a rxcmdn/r/wn/statenn/bufenn/cldn/dldn /mdtn, codenn to stroben 1t t7b as 7a from stroben - 1t t8 rxcmdn - to incmd 4t t9 incmdn to statenn 3t t10 valcrn pulse width 5t t11 valdrn to dtrqn 1t t12 dtrqn to dtakn (rxdata) 0 3t t13 dtakn to bufenn 1t 2t t14 dtrqn - to cldn 24t t15 cldn - to gbrn 15t 16t t16 cldn to status valid bus b0:b15 100 ns t17 cldn - to status invalid on b0:b15 35 ns t18 dtrqn - to dtakn - 0 t19 statenn to cldn non mode data 11t 12t t20 cldn - to dtrqn 15t t21 dtrqn to dtakn (tx data) 0 54t t22 valdrn to r/wn 2t 3t t23 mdtn to cldn 24t t24 cldn - to mdrn 14t t25 statenn to cldn mode data 11t 12t t26 cldn - to mdtn 15t 16t t27 mdtn - to incmdn - 77t 78t t28 dtrqn - to incmdn - (non broadcast) 77t 78t t29 dtrqn - to incmdn - (broadcast) 25t t30 mdtn - to incmdn - (broadcast) 25t t31 cldn - to incmdn - (mode) 11t 12t t32 cldn - to txenn 1t 2t t33 txenn/pdoutn/ndoutn/prop delay difference 6 ns t34 start of transmission to eotn - 76t 12 t34a end of transmission to eotn 82t 12 t35 end of transmission to abortn 1) rt1 = 0 rt0 = 0 20 us 2) rt1 = 0 rt0 = 1 26 us 3) rt1 = 1 rt0 = 0 48 us 4) rt1 = 1 rt0 = 1 112 us t36 minimum no response timeout 1) rt1 = 0 rt0 = 0 15.75 16.25 us 2) rt1 = 0 rt0 = 1 21.75 22.25 us 3) rt1 = 1 rt0 = 0 43.75 44.25 us 4) rt1 = 1 rt0 = 1 107.75 108.25 us t37 remote terminal response time 10.3 11.25 us t38 minimum pucn pulse width 20 ns t39 pucn to reset 90 ns figure 12: ac electrical characteristics
ma3690/1/3 18/41 symbol description min. typ. max. units t40 resetn to aden 80 ns t41 pucn - to resetn - 2t t42 resetn - to adenn - 2t 2t + 80 ns t43 initialisation word set-up wrt resetn - 15 ns t44 initialisation word hold wrt resetn - 20 ns t45 minimum resetn pulse width 90 ns t46 minimum ck12 high 33 ns t47 minimum ck12 low 20 ns t48 ck12 - to ck4 - 90 ns t49 ck12 to ck4 90 ns t50 haltreqn pulse width 1t t51 haltreqn - to haltedn - 55 ns t52 haltreqn - to codenn 1t 2t t53 codenn - to codenn 2t t54 rt-rt minimum validation time 1) rt1 = 0 rt0 = 0 55.75 56.25 us 2) rt1 = 0 rt0 = 1 61 75 62.25 us 3) rt1 = 1 rt0 = 0 83.75 84.25 us 4) rt1 = 1 rt0 = 1 147.75 148.25 us t55 haltreqn setup for next message wrt to incmdn - 150 ns t56 r/wn to r/wn rt-bc report cycle 80t t57 bufenn - to bufenn data word to report word 29t t58 bc intermessage gap 1) without a no operation instruction 20 us 2) with a no operation instruction 28 us t59 codenn interval high between received status 24t and report word during report cycle t60 codenn interval between report word and 6t next message fetch for continuous operation t61 coden interval between bc noop data pointer fetch and report word 5t t62 incmdn - to incaddrn 1t t63 busyreqn to busyackn 60 ns t64 busyreqn - to busyackn - 60 ns t65 incmdn - to busyackn 60 ns t66 incmdn - to busyackn - 100 ns t67 ck4 - to r/wn/bufenn/co/c1/codenn/mdtn 115 ns mil-std-883, method 5005, subgroups 9, 10, 11 notes: 1. t = ck4 period, t 12 = ck12 period 2. times quoted as typical means a fixed number of ck4 clock cycles but excludes slight variations due to propagation delays. conditions: v dd = 4.5 to 5.5v, t amb = -55 c to +125 c, v il = 0v, v ih = 4v, v out threshold = 1.5v except t 2 where measured by a 1v change in output voltage. load = 50pf except t 2 where additional 1k load to 0v or v dd . figure 12: ac electrical characteristics (continued)
ma3690/1/3 19/41 list of timings 14 clock timing 15 power up clear initialisation 16 subsystem reset 17 minimum no response timeout 18 abort 19 start of transmission detect 20 end of transmission detect 21 rt command reception and subsystem status read 22 bc-rt data transfer (non mode) + status 23 rt status + rt-bc data transfer (non mode) 24 received mode data transfer + status 25 rt status + transfer mode data transfer 26 broadcast bc-rt data transfer (non mode) 27 rt-broadcast received mode data transfer 28 mode command no data (tir) 29 remote terminal response time 30 rt-rt validation timeout 31 remote terminal busy handshake 32 rt status load 33 bc-message fetch sequence 34 bc-report cycle (shown for rt-rt no data to subsystem) 35 rt-bc report cycle 36 bc intermessage gap 37 bc-no operation 38 bc-self test (report sequence) 39 bc-passive monitor 40 bc-retry 41 bc-data transfer handshake figure 13: list of timings timing diagrams figure 14: clock timing
ma3690/1/3 20/41 figure 15: power up clear initialisation note: if the first command to the rt following power up is to be tlsw then initialisation should be via puc. puc is driven by the subsystem. figure 16: subsystem reset * reset must be driven from subsystem via an open drain/ collector device
ma3690/1/3 21/41 figure 17: minimum no response timeout this value is programmable using the rt0/rt1 inputs figure 19: start of transmission detect note: detection is sync + 3 data bits figure 18: abort this sequence will also occur at the end of each message unless a new message is received.
ma3690/1/3 22/41 figure 20: end of transmission detect figure 21: rt command reception and subsystem status read note: quote time pulse as typical, except t 1 , t 2 , t 3 and t 4 .
ma3690/1/3 23/41 figure 22: bc-rt data transfer (non-mode) + status figure 23: rt status + rt-bc data transfer (non mode) note: for successive data words dtrq to dtrq = 80 x ck4 periods (20 m s)
ma3690/1/3 24/41 figure 24: received mode data transfer + status figure 25: rt status + transfer mode data transfer note: exception mdt is not active for tlc, tbit
ma3690/1/3 25/41 figure 26: broadcast bc-rt data transfer (non mode) figure 27: rt-broadcast received mode data transfer note: mdt, mdr are not active for m/c stsd and orstsd
ma3690/1/3 26/41 figure 28: mode command no data (tir) note: 1. sync m/c. 2. self test m/c - takes 668 m s from end of status transmission on 1553 bus. 3. reset m/c/ - reset pulse 3 x ck4 after txcn - this prevents abort pulse following this command and fires eot high and remains high. figure 29: remote terminal response time figure 30: rt-rt validation timeout
ma3690/1/3 27/41 figure 31: remote terminal busy handshake figure 32: rt status load
ma3690/1/3 28/41 figure 33: bc-message fetch sequence note: bufen is not active for the data pointer word as the 3690/1 does not use the word. it is required by subsystem only.
ma3690/1/3 29/41 figure 34: bc-report cycle (shown for rt-rt no data to subsystem) note: for data to subsystem gbr (no mode) or mdr (mode data) will pulse as shown - otherwise gbr , mdr do not pulse
ma3690/1/3 30/41 figure 35: rt-bc report cycle figure 36: bc intermessage gap
ma3690/1/3 31/41 figure 37: bc - no operation
ma3690/1/3 32/41 figure 38: bc - self test (report sequence) figure 39: bc - passive monitor
ma3690/1/3 33/41 figure 40: bc - retry note: the message fetch sequence is not repeated for any retries. it is therefore essential that the subsystem zeros the data word address counter for each retry. this is simply achieved by using cld to clear the counter and dtak to increment the counter. figure 41: bc - data transfer handshake
ma3690/1/3 34/41 outlines figure 42a: 48-lead ceramic dil (solder seal) - package style c ref. min. nom. max. a - - 4.37 (0.172) a 1 1.016 (0.04) - 1.53 (0.060) b 0.40 (0.016) - 0.508 (0.020) c 0.20 (0.009) - 0.305 (0.012) d - - 61.57 (2.424) e - 2.54 (0.100) - e 1 - 15.24 (0.600) - h 4.71 (0.185) - 5.38 (0.212) m e - - 15.75 (0.620) w - - 1.53 (0.060) dimensions in mm (inches) gps xg426
ma3690/1/3 35/41 figure 42b: 48-lead ceramic dil (solder seal) - package style c note: on the ma3693 rt1 is replaced by terminal flag tfn (ttl output) transceiver chip (ma3690) terminal controller chip (ma3691) see note -
ma3690/1/3 36/41 figure 42c: 48-lead ceramic dil (solder seal) - package style c transceiver chip (ma3693) (for applications that require access to terminal flag) see note - note: the ma3693 has terminal flag (tfn) latched signal output on pin 13 (ttl). this replaces the rt1 signal input that is used on the ma3690 standard version.
ma3690/1/3 37/41 figure 43a: 64-lead topbraze flatpack (package style f) ref. min. nom. max. a - - 2.1 (0.083) a 1 0.96 (0.038) - 1.07 (0.042) b 0.41 (0.016) - 0.51 (0.020) c 0.178 (0.007) - 0.254 (0.010) d1,d2 - - 23.11 (0.910) e 15.54 (0.612) - 15.95 (0.628) e - 1.27 (0.050) - l 8.89 (0.350) - 9.27 (0.365) z 1.73 (0.068) - 2.16 (0.085) dimensions in mm (inches) gps xg487
ma3690/1/3 38/41 figure 43b: 64-lead topbraze flatpack (package style f)
ma3690/1/3 39/41 figure 43c: 64-lead topbraze flatpack (package style f)
ma3690/1/3 40/41 radiation tolerance total dose radiation testing for product procured to guaranteed total dose radiation levels, each wafer lot will be approved when all sample devices from each lot pass the total dose radiation test. the sample devices will be subjected to the total dose radiation level (cobalt-60 source), defined by the ordering code, and must continue to meet the electrical parameters specified in the data sheet. electrical tests, pre and post irradiation, will be read and recorded. gec plessey semiconductors can provide radiation testing compliant with mil-std-883 test method 1019, ionizing radiation (total dose). total dose (function to specification)* 3x10 5 rad(si) transient upset (stored data loss) 5x10 10 rad(si)/sec transient upset (survivability) >1x10 12 rad(si)/sec neutron hardness (function to specification) >1x10 15 n/cm 2 single event upset** <1x10 -10 errors/bit day latch up not possible * other total dose radiation levels available on request ** worst case galactic cosmic ray upset - interplanetary/high altitude orbit figure 44: radiation hardness parameters ordering information unique circuit designator s r q h radiation hard processing 100 krads (si) guaranteed 300 krads (si) guaranteed 1000 krads (si) guaranteed radiation tolerance c f n ceramic dil (solder seal) flatpack (solder seal) naked die package type qa/qci process (see section 9 part 4) test process (see section 9 part 3) assembly process (see section 9 part 2) l c d e b s rel 0 rel 1 rel 2 rel 3/4/5/stack class b class s reliability level max3690xxxxx max3691xxxxx max3693cxxxx for details of reliability, qa/qc, test and assembly options, see manufacturing capability and quality assurance standards section 9.
ma3690/1/3 41/41 customer service centres france, benelux, italy and spain tel: +33 (0)1 69 18 90 00. fax: +33 (0)1 64 46 54 50 north america tel: 011-800-5554-5554. fax: 011-800-5444-5444 uk, germany, scandinavia & rest of world tel: +44 (0)1522 500500. fax: +44 (0)1522 500020 sales offices france, benelux, italy and spain tel: +33 (0)1 69 18 90 00. fax: +33 (0)1 64 46 54 50 germany tel: 07351 827723 north america tel: (613) 723-7035. fax: (613) 723-1518. toll free: 1.888.33.dynex (39639) / tel: (831) 440-1988. fax: (831) 440-1989 / tel: (949) 733-3005. fax: (949) 733-2986. uk, germany, scandinavia & rest of world tel: +44 (0)1522 500500. fax: +44 (0)1522 500020 these offices are supported by representatives and distributors in many countries world-wide. ? dynex semiconductor 2000 publication no. ds3587-5 issue no. 5.0 january 2000 technical documentation C not for resale. printed in united kingdom headquarters operations dynex semiconductor ltd doddington road, lincoln. lincolnshire. ln6 3lf. united kingdom. tel: 00-44-(0)1522-500500 fax: 00-44-(0)1522-500550 dynex power inc. unit 7 - 58 antares drive, nepean, ontario, canada k2e 7w6. tel: 613.723.7035 fax: 613.723.1518 toll free: 1.888.33.dynex (39639) this publication is issued to provide information only which (unless agreed by the company in writing) may not be used, applied or reproduced for any purpose nor form part of any order or contract nor to be regarded as a representation relating to the products or services concerned. no warranty or guarantee express or implied is made regard ing the capability, performance or suitability of any product or service. the company reserves the right to alter without prior notice the specification, design or price of any product or service. information con cerning possible methods of use is provided as a guide only and does not constitute any guarantee that such methods of use will be satisfactory in a specific piece of equipment. it is the user's responsibility to f ully determine the performance and suitability of any equipment using such information and to ensure that any publication or data used is up to date and has not been superseded. these products are not suitable for use in any medical products whose failure to perform may result in significant injury or death to the user. all products and materials are sold and services provided subject to the company's conditions of sale, w hich are available on request. all brand names and product names used in this publication are trademarks, registered trademarks or trade names of their respec tive owners. http://www.dynexsemi.com e-mail: power_solutions@dynexsemi.com datasheet annotations: dynex semiconductor annotate datasheets in the top right hard corner of the front page, to indicate product status. the annota tions are as follows:- target information: this is the most tentative form of information and represents a very preliminary specification. no actual design work on the product has been started. preliminary information: the product is in design and development. the datasheet represents the product as it is understood but details may change. advance information: the product design is complete and final characterisation for volume production is well in hand. no annotation: the product parameters are fixed and the product is available to datasheet specification.


▲Up To Search▲   

 
Price & Availability of MAS3690CS

All Rights Reserved © IC-ON-LINE 2003 - 2022  

[Add Bookmark] [Contact Us] [Link exchange] [Privacy policy]
Mirror Sites :  [www.datasheet.hk]   [www.maxim4u.com]  [www.ic-on-line.cn] [www.ic-on-line.com] [www.ic-on-line.net] [www.alldatasheet.com.cn] [www.gdcy.com]  [www.gdcy.net]


 . . . . .
  We use cookies to deliver the best possible web experience and assist with our advertising efforts. By continuing to use this site, you consent to the use of cookies. For more information on cookies, please take a look at our Privacy Policy. X